When trying to execute a Scheduled Task (even one that used to work okay) you see the following in the Scheduled Tasks log file:The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.The specific error is:0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.This means the database that holds the security and credential information for the Scheduled Tasks is missing or has become corrupted.If you proceed to resolve the issue, you will have to reenter the Scheduled Task password for all of your Scheduled Tasks, so you might want to be sure you know what all the account settings are for each of your Scheduled Tasks before you start or they will not work.It doesn't really matter - since the Scheduled Tasks don't work anyway... (under what user account and password is each Scheduled Task set up?) Stop the Task Scheduler Service.Using Windows search (or explore manually), find the folder containing the Scheduled Task security information.The folder to search for and locate is called:S-1-5-18 Depending on your installation, there may be several folders with that name, but you are only interested in one of them. The one you need to work on is the "All Users" copy and should be in one of these folders:C:\Documents and Settings\All Users.WINDOWS\Application Data\Microsoft\Crypto\RSA <-- this works for my installation or perhaps for your installation, this folder:C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA When inside the RSA folder, rename the S-1-5-18 folder to something you can remember, like:S-1-5-18.bakWith the Task Scheduler stopped, now would be a good time to delete the old Scheduled Tasks log file which is here:c:\Windows\SchedLgU.txt (rename or delete the old log file)Restart the Task Scheduler Service and check the Scheduled Tasks log file and it should look something like this:"Task Scheduler Service" Started at 1/1/2011 4:35:08 PMEvery Scheduled Task you have will now need to have the account password entered again (even though the Scheduled Tasks "look" okay).When you establish the credentials for the first Scheduled Task, a new S-1-5-18 folder will be created automatically.Right click each Scheduled Task, choose Properties and Set (or reSET) the password on each Scheduled Tasks again, click Apply and OK to save the settings. You will have to do this for every Scheduled Task.See if your afflicted Scheduled Task will now run both manually and automatically.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Using WinXP Home SP3 version 2002. I get the above error when trying to schedule a task. I have stopped task scheduler service and deleted the log. I have restarted the service and tried to schedule a simple task and got this error, even when I tried to manually run the task when it expired. I am running this under my Admin account and password; I pasted a copy of Schedlgu showing the results when I just now manually ran the scheduled task command prompt as a test.Any suggestions are greatly appreciated and thanks...Joe"Task Scheduler Service" Started at 2/3/2011 1:11:27 PM"Command Prompt.job" (cmd.exe) 2/3/2011 1:11:39 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.[ ***** Most recent entry is above this line ***** ] Joe1 person needs an answerI do too

Thank you, Jose. I will try thisJoe

Well, if it doesn't work, I need to change my directions so they do work(The sniper in me advocates the one shot, one kill method of problem solving)Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

When trying to execute a Scheduled Task (even one that used to work okay) you see the following in the Scheduled Tasks log file:The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.The specific error is:0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.This means the database that holds the security and credential information for the Scheduled Tasks has become corrupted.If you proceed to resolve the issue, you will have to reenter the Scheduled Task password for all of your Scheduled Tasks, so you might want to be sure you know what all the account settings are for each of your Scheduled Tasks before you start or they will not work.It doesn't really matter - since the Scheduled Tasks don't work anyway... (under what user account and password is each Scheduled Task set up?) Stop the Task Scheduler Service.Using Windows search (or explore manually), find the folder containing the Scheduled Task security information.The folder to search for and locate is called:S-1-5-18 Depending on your installation, there may be several folders with that name, but you are only interested in one of them. The one you need to work on is the "All Users" copy and should be in one of these folders:C:\Documents and Settings\All Users.WINDOWS\Application Data\Microsoft\Crypto\RSA <-- this works for my installation or perhaps for your installation, this folder:C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA When inside the RSA folder, rename the S-1-5-18 folder to something you can remember, like:S-1-5-18.bakWith the Task Scheduler stopped, now would be a good time to delete the old Scheduled Tasks log file which is here:c:\Windows\SchedLgU.txt (rename or delete the old log file)Restart the Task Scheduler Service and check the Scheduled Tasks log file and it should look something like this:"Task Scheduler Service" Started at 1/1/2011 4:35:08 PMEvery Scheduled Task you have will now need to have the account password entered again (even though the Scheduled Tasks "look" okay).When you establish the credentials for the first Scheduled Task, a new S-1-5-18 folder will be created automatically.Right click each Scheduled Task, choose Properties and Set (or reSET) the password on each Scheduled Tasks again, click Apply and OK to save the settings. You will have to do this for every Scheduled Task.See if your afflicted Scheduled Task will now run both manually and automatically.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Jose, I found the S-1-5-18 folder in the RSA folder and renamed it. The path was C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA. I stopped task scheduler service and deleted the log. Here is the log after restarting task scheduler and it did create a new S-1-5-18 folder. I use one and only one password on this machine and each scheduled task uses the same password. Do you have another suggestion? Thank you so much for your continued help...Joe"Task Scheduler Service" Started at 2/3/2011 5:53:11 PM"User_Feed_Synchronization-{C0A70D48-4FCD-4F19-9623-607F73D3E60E}.job" (msfeedssync.exe) 2/3/2011 5:55:00 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x80070534: No mapping between account names and security IDs was done."User_Feed_Synchronization-{C0A70D48-4FCD-4F19-9623-607F73D3E60E}.job" (msfeedssync.exe) 2/3/2011 6:00:00 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x80070534: No mapping between account names and security IDs was done."defrag.job" (defrag.exe) 2/3/2011 6:02:54 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated."User_Feed_Synchronization-{C0A70D48-4FCD-4F19-9623-607F73D3E60E}.job" (msfeedssync.exe) 2/3/2011 6:05:00 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x80070534: No mapping between account names and security IDs was done."Command Prompt.job" (cmd.exe) 2/3/2011 6:05:10 PM ** ERROR ** The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task. The specific error is: 0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.[ ***** Most recent entry is above this line ***** ] Joe

Hmmm. Let's stick with your Command Prompt job since it is fairly simple and see if we can get that working.What is your XP version and Service Pack?What is your current antivirus antimalware configuration?If the tasks used to work, what do you think might have changed since the last time they worked properly?It would not hurt to run some scans for malicious software:Download, install, update and do a full scan with these free malware detection programs:Malwarebytes (MBAM): http://malwarebytes.org/SUPERAntiSpyware: (SAS): http://www.superantispyware.com/They can be uninstalled later if desired.It could be my instructions are out of whack since I have only seen this problem twice before but did recreate it on my system today and also have the Command Prompt job for testing STs, and got the same error message (and then fixed it as I think I described).It still looks like the ST database is messed up somehow. Did you find any other S-5-1-18 folders? On my system, I stopped the service, renamed the S-5-1-18 folder, restarted the service and tried to run the task (and got the error).Then I entered the Password for my Command Prompt task and that was the moment when the new S-5-1-18 folder was created. Restarting the service did not create the new folder - I had to actually manipulate a task. Is that what you noticed?After I entered the password again, the folder was created and then the Command Prompt task worked fine.Are you able to just delete the Command Prompt task completely and make a new one? I think the Set password part was the only thing I needed to redo on my Command Prompt task and then the new S-5-1-18 folder magically appeared. Is that what you noticed (repeat the process if you are not sure). It looks like you found some of my old post somewhere on the Internet about starting with the simple Command Prompt task!It could be that there is some other step I need to add to my method.Please double check the process and see if you can get your Command Prompt task to work and I will look around some more and at mine again too. It will not hurt to go through the process again of whacking the S-5-1-18 folder, etc.Do you find more S-5-1-18 folders? Maybe those are the ones you need to be looking at, but I am pretty sure it is just the All Users one, but that may not be the same on your system. The one that did the trick for me was where I indicated and I believe yours is where you indicated.Maybe my method only works on my system because my system is afraid of me.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

I will try the above. I originally had created the task for disk defrag and I don't believe it ever worked. I did find one other S-1-5-18 folder. I'm using WP Home Edition version 2002 SP3. My antivirus/antimalware is AVG Free Edition from Grisoft/Ad Aware Free from Lavasoft. AVG updates and scans daily through its scheduler. I have to manually update and scan Ad Aware, usually 2-3 times a week, because it uses the task scheduler. I'll try the above suggestions including the downloads. I didn't really notice when the new folder was created, since I only liiked after restarting the service. I have tried deleting and adding the command prompt task after making changes and nothing changed.I'll let you know if these next steps work. Maybe you can intimidate my system too.Joe

A defrag task can sometimes be tricky - sometimes because it is misunderstood and works as designed which is not always as desired... but we can fix that later.I found my S-1-5-8 folder again, stopped the service, renamed the folder (I first deleted the old S-1-5-8.bak folder from before of course), started the service and no new S-1-5-8 folder was created. That makes sense since it is the task credentials that get saved in the S-1-5-8 folder and we need to set them next.Then I went to my Command Prompt task and redid the username and password (I believe all you need is the password), clicked Apply and then at that moment, the new S-1-5-8 folder was created and then the Command Prompt task started just fine, so be sure that is the way things look for you.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Hi Jose, first off, I did updates and complete scans with my AVG and Ad Aware. Then i downloaded Malwarebytes and Super antiSpyware and did complete scans again. Nothing but the usual tracking cookies were found. I will try these latest suggestions in the way you specify and let you know. ThanksJoe

At this point I really don't think scheduled tasks ever worked. It's something I've only recently, in the last couple of months, tried to use. It works fine on my wife's Win7 machine. Do you think there is any use adding a new administrator account and password, deleting the old account, and trying to create a task on the new account?Joe

That is not what I noticed here and I did recreate your error by afflicting my credentianls on purpose. What I posted before was from my own ST log file, then I fixed it. You already had some tasks and have XP Home...,I usually don't have any tasks (except my Command Prompt task for testing) and have XP Pro. Hmmm.It is curious that your folder was created starting the Service and mine was not but I will look at it again. I thought I was looking right at it!You can sure create another Administrator type account and see if it works differently.Let me look at it again and think about that (it may take me a little while).Maybe somebody else has some ideas.No sir, can't say that I like it.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Okay - I don't think it is a malicious software problem, but it doesn't make sense to me to try to fix things unless you are reasonbly sure the system is not afflicted with malware.SAS loves those cookies!Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Hi Jose, Here's what happened:1. I deleted the S-1-5-18.bak folder2. I stopped Task Scheduler Service3. I renamed S-1-5-18 folder S-1-5-18.bak4.I started task scheduler; at this time I looked in RSA folder and a new S-1-5-18 folder was already created.5. I created a new scheduled command prompt task and retyped the username and password, and got the same error and it failed to run when I manually tried to run it.Looks like a departure from your findings. If you're out of ideas, that's ok. It is a laptop I use for my repair business, and this is just a convenience for me. i won't make it or break on this little issue.Joe

I did create a new Admin account with a different password. I deleted the old scheduled command prompt before creating the new account. I get the exact same error on the new Admin account trying to schedule or manually run command prompt. Maybe XP Home won't allow a scheduled task???Joe